Five things landed on you this week, and you said yes to all five. Here is how it ends: three get done well, one gets done late, and one quietly disappears while you hope nobody remembers asking for it. The dropping already happened back at the moment you said yes to everything. The only thing still undecided is whether anybody else heard you decide it.
The experiment where people picked the worse task on purpose
Meng Zhu, Yang Yang, and Christopher Hsee ran five experiments testing how people choose between tasks. Participants consistently picked the task with the shorter deadline over the task with the bigger payoff, even when they had been told outright which one was worth more. The researchers named it the mere urgency effect, and it violates the most basic rule of rational choice: people knowingly selected the option that paid them less.
Zhu's explanation is that a closing window creates a pull all its own, so people focus on the timeframe until "they lose sight of the outcomes".
That is why your task list ends up sorted by deadline, with value playing no part in it, and you never chose that order. Every request arrives wearing the same red flag. The loudest one wins, the work that would have mattered slides to next week, and you never made a decision you could defend because you never made a decision at all.
The day Lou Gerstner told reporters what he was not going to do
July 27, 1993. Lou Gerstner, about a hundred days into the IBM job, stood in front of the press and announced an $8 billion quarterly loss, a restructuring including 50,000 early retirements, and a dividend cut. Reporters wanted the other thing they had been promised: the vision.
He told them that "the last thing IBM needs right now is a vision", then named what would get the attention instead, which was restoring the company to profitability with market-driven strategies for each business.
The coverage punished him. Commentators pointed out the stock had fallen since he arrived and said he had done nothing. He absorbed that in public, on the record, in the same week he was cutting tens of thousands of jobs. He could have said something vague about vision coming soon and let the press fill in the blank. Naming the casualty cost him a bad news cycle and bought him eighteen months of freedom to fix the balance sheet. By his retirement in 2002, IBM's market value had gone from $29 billion to $168 billion.
The turnaround is famous. The move worth stealing was smaller and happened in that press room when he put his name on the thing that would not get done.
Quiet dropping reads as incompetence. Announced dropping reads as judgment.
Here is the asymmetry nobody explains to you. When something slips silently, your manager finds out at the worst possible moment, usually from a third party, usually too late to react. What they conclude is that you could not carry the load.
Name the same slip three days earlier, and they conclude something entirely different: that you can rank, forecast, and communicate. Those three things are the job description of the person they promote next. Identical missed deadline. Opposite conclusions about you.
The trade sentence you can send in twenty seconds
One formula covers almost every version of this:
"If [new thing], then [specific existing thing] moves to [specific date]. Want me to make that trade?"
Three parts make it work. It names a specific casualty, and "I'm swamped" gives your manager nothing to decide on. It attaches a real date, so there is something to hold you to. And it ends in a question, which returns the decision to the person who actually owns the priorities.
Compare the two versions. "I'll try to fit it in." Against: "I can take the vendor deck if the QBR numbers move to Tuesday the 9th. Want me to make that trade?" Same fifteen seconds of typing. Completely different picture of who is running the queue.
Three questions that break the tie when everything is red
Ranking gets hard because five urgent things feel identical from the inside. Run each one through these:
- Who is blocked right now if this is late? Work that unblocks other people outranks work that only affects you.
- What actually breaks if this is a week late? If the honest answer is nothing, the task is loud, not urgent.
- Could someone else do this acceptably? If yes, this belongs in a handoff conversation.
Then show the ranking. A ranked list invites a correction. A complaint about workload invites a shrug.
When your manager says all of it is priority one
Some managers genuinely will not choose. Give them a smaller decision to make:
"Here's the order I'd run these in: A, then B, then C. If that's wrong, tell me which one goes to the top, and I'll move the others down."
That sentence proves you have already done the thinking and hands the tradeoff to the person who can see across the whole team, which you cannot. Whatever they say, write it back in one line the same day: "Confirming, B first, A moves to the 14th." Now the decision exists in writing and belongs to both of you.
Your move before Thursday
Send one message at the start of next week. Skip the status update and send a trade note:
"This week I'm landing [A] and [B]. [C] moves to [date] so those two land properly. Flag now if that order is wrong."
Three lines, sent before anyone has to come asking where something is. Send it Monday, then send it again the Monday after. The second one is when people start treating your dates as real numbers.
Until next time, Future Leader.
